<html>
<head><meta charset="utf-8"><title>followup on 04.30 meeting · t-compiler/wg-rustc-dev-guide · Zulip Chat Archive</title></head>
<h2>Stream: <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/index.html">t-compiler/wg-rustc-dev-guide</a></h2>
<h3>Topic: <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/followup.20on.2004.2E30.20meeting.html">followup on 04.30 meeting</a></h3>

<hr>

<base href="https://rust-lang.zulipchat.com">

<head><link href="https://rust-lang.github.io/zulip_archive/style.css" rel="stylesheet"></head>

<a name="165003076"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/followup%20on%2004.30%20meeting/near/165003076" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> mark-i-m <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/followup.20on.2004.2E30.20meeting.html#165003076">(May 06 2019 at 17:51)</a>:</h4>
<p>Hi, I missed the meeting and just read the meeting notes topic... a lot of interesting ideas there!</p>
<p>Some thoughts I had:</p>
<ul>
<li>I'm wary of adding a walkthrough/tour chapter without first discussing what the final organization of rustc-guide should look like. In particular, we already have "walkthrough of contributing to rustc" and "high level overview of the compiler" chapters.</li>
<li>I think part of what makes the rustc-guide feel disorganized is that there is no "flow". Each chapter was written by a different person, and there is no common narrative flowing through it. Moreover, each chapter is organized differently.<ul>
<li>One solution to this might be to decide that each chapter will be organized the same way. e.g...<ul>
<li>The top level chapter will explain the contents of whole chapter (like a detailed Table of Contents for that chapter)</li>
<li>The first sub-chapter should be a high-level overview of the technical content</li>
<li>All subsequent sub-chapters contain the actual technical content of the chapter</li>
</ul>
</li>
</ul>
</li>
<li>I think having a "here is the path your program takes through rustc" chapter is a great idea, as it helps put all the pieces into context.</li>
</ul>



<a name="165003292"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/followup%20on%2004.30%20meeting/near/165003292" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> mark-i-m <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/followup.20on.2004.2E30.20meeting.html#165003292">(May 06 2019 at 17:53)</a>:</h4>
<p>A couple of other issue that would be nice to address</p>
<ul>
<li>The rustc-guide repo has a ton of issues on it that need work (this is admittedly boring work and some of it requires expertise).<ul>
<li>It would be good to develop a plan to deal with these issues.</li>
<li>It would be good triage the issues.</li>
</ul>
</li>
<li>There are a lot of missing (important) chapters (e.g. macros, LLVM/codegen, etc)<ul>
<li>Is the plan to get this content from the video lecture series?</li>
</ul>
</li>
</ul>



<a name="165003407"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/followup%20on%2004.30%20meeting/near/165003407" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> mark-i-m <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/followup.20on.2004.2E30.20meeting.html#165003407">(May 06 2019 at 17:55)</a>:</h4>
<p>thoughts?</p>



<a name="165003426"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/followup%20on%2004.30%20meeting/near/165003426" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Santiago Pastorino <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/followup.20on.2004.2E30.20meeting.html#165003426">(May 06 2019 at 17:55)</a>:</h4>
<p>agree 100% :)</p>



<a name="165003434"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/followup%20on%2004.30%20meeting/near/165003434" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Santiago Pastorino <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/followup.20on.2004.2E30.20meeting.html#165003434">(May 06 2019 at 17:55)</a>:</h4>
<p>in particular ...</p>



<a name="165003437"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/followup%20on%2004.30%20meeting/near/165003437" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Santiago Pastorino <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/followup.20on.2004.2E30.20meeting.html#165003437">(May 06 2019 at 17:55)</a>:</h4>
<blockquote>
<p>I'm wary of adding a walkthrough/tour chapter without first discussing what the final organization of rustc-guide should look like. In particular, we already have "walkthrough of contributing to rustc" and "high level overview of the compiler" chapters.</p>
</blockquote>



<a name="165003512"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/followup%20on%2004.30%20meeting/near/165003512" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Santiago Pastorino <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/followup.20on.2004.2E30.20meeting.html#165003512">(May 06 2019 at 17:56)</a>:</h4>
<p>yes, the final organization of rustc-guide needs to be discussed probably before doing the walkthrough</p>



<a name="165006968"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/196385-t-compiler/wg-rustc-dev-guide/topic/followup%20on%2004.30%20meeting/near/165006968" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> amanjeev <a href="https://rust-lang.github.io/zulip_archive/stream/196385-t-compiler/wg-rustc-dev-guide/topic/followup.20on.2004.2E30.20meeting.html#165006968">(May 06 2019 at 18:36)</a>:</h4>
<p>Makes sense to me. Also not an expert in any of the topics so willing to do yak shaving if need be. <span aria-label="smiley" class="emoji emoji-1f603" role="img" title="smiley">:smiley:</span></p>



<hr><p>Last updated: Aug 07 2021 at 22:04 UTC</p>
</html>